Still does not work...

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

Thank you for your suggestion. Here is a bit more information about this.

After testing with databases on the B2 version I got the following situation:
Two large databases were DAOS enabled and the .nlo attachments were successfully created in the DAOS directory specified in the server document. Everyting was working great – and to be honest I had the feeling that the DAOS was too good to be true :- )

After I upgraded the server to the newly released version of Lotus Domino 8.5 the DAOS was unable to create a new .nlo files. It did not matter if I tried to do it on the databases tested with the B2 version or new databases I created to test.

Then I deleted about 50% of the documents from the databases tested with the B2 version. After the document deletion I ran the “tell daosmgr prune 0” command.
This seemed to be working as expected because a lot of .nlo files were removed from the DAOS directory specified.

Then I ran the server command “load compact gpcase.nsf –c –daos off” to disable the database from DAOS. This also seemed to be working fine. The physical size of the .nsf file got greatly increased and the .nlo files were removed from the directory. I did this for both the databases I had been testing with the B2 version.

At this stage no file was left in the DAOS directory specified in the server document.

So at this point everything in DAOS seemed to be working for me expect creating the .nlo files for the new attachments.

Then I tried to create a new database and enable that database for DAOS. I still got the same error when trying to add attachments to a document in this database. I tried enabling them by selecting the database property and also by running the “load compact disc.nsf –c –daos on” server command. Both of this gave me the same result.

Then I tried to change the location of the DAOS directory specified in the server document and that did not help either.

Then I tried the items you suggested and this also did not help. It gave my the same result (except the DAOS seemed to have been initialised – so that the new DAOS subdirectory was called “0001”)

In addition I stopped the Domino server, renamed the “daoscat.nsf” file in the data directory to “daoscat.nsf.bak”. Restarted the server and tried again but this did not help.

I un-installed the Domino server, removed all the files in the directory specified for the transaction logging, renamed the “daos.cfg” to “daos.cfg.bak”, and renamed the “daoscat.nsf” to “daoscat.nsf.bak”. Installed the server again and created a new database on the server. Enabled the server via the database properties and added a document to the database whic included an attachment and when I saved the document I get the following”:

12/01/2009 10:39:19 The database D:\Lotus\Domino85\data\Disc.nsf was unable to
write to file D:\TEST\DAOS\0001\8FE48147961676FAC125753C00350A0818FE48147961676
P.nlo: Release 8.5 December 05, 2008

The “D:\TEST\DAOS\0001” directory was created by the DAOS task but not the .nlo file itself.

There is no anti-virus software running on the server which could prevent the .nlo file from being created.

Is there a place where I can look for a detailed reason for this message – that is why the .nlo file could not be created ?

Feedback response number WEBB7N8DQ6 created by ~Mary Chuhipivitch on 01/12/2009